DSTU2
This page is part of the FHIR Specification (v1.0.2: DSTU 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions 
SDC Data Elements author/maintenance system
{
"resourceType": "Conformance",
"id": "conformance-sdc-de-curator",
"text": {
"status": "generated",
"div": "<div>\n \n <h2>SDC Data Element Curator</h2>\n \n <p>(Requirements Definition)</p>\n \n <p>Published: 2014-07-06 (draft)</p>\n \n <p>Published by: \n <b>U.S. Office of the National Coordinator (ONC)</b>\n \n </p>\n \n <p>This profile defines the expected capabilities of the \n <i>SDC Data Element Curator</i> role when conforming to the S&I Framework's \n <a href=\"sdc.html\">Structured Data Capture FHIR Data Element Exchange implementation guide</a>. This role is responsible for defining and updating data elements stored in a repository.\n </p>\n \n <h2>General</h2>\n \n <table>\n \n <tbody>\n \n <tr>\n \n <th>FHIR Version:</th>\n \n <td>1.0.2</td>\n \n </tr>\n \n <tr>\n \n <th>Supported formats:</th>\n \n <td>xml, json</td>\n \n </tr>\n \n </tbody>\n \n </table>\n \n <h2>REST behavior</h2>\n \n <p>The primary focus of the curator is the definition and maintenance of \n <a href=\"../dataelement.html\">DataElement</a>s. However, \n <a href=\"../valueset.html\">ValueSet</a>s must also be supported to allow definition of coded data elements. Some data elements will choose to maintain value sets as 'contained' resources, meaning the value set exists only in the context of the data element and cannot be referenced or maintained without also updating the data element. However, systems should support value set re-use across data elements. (Version-specific referencing can be used to avoid value sets from changing independent of the referencing \n <a href=\"../questionnaire.html\">Questionnaire</a>.)\n </p>\n \n <p>\n \n <b>Security:</b>\n \n </p>\n \n <p>Implementations must meet the general security requirements documented in the \n <a href=\"sdc-security.html\">SDC implementation guide</a>.\n </p>\n \n <h3>Resource summary</h3>\n \n <table class=\"grid\">\n \n <thead>\n \n <tr>\n \n <th>Resource</th>\n \n <th>Search</th>\n \n <th>Read</th>\n \n <th>Read Version</th>\n \n <th>Instance History</th>\n \n <th>Resource History</th>\n \n <th>Create</th>\n \n <th>Update</th>\n \n <th>Delete</th>\n \n </tr>\n \n </thead>\n \n <tbody>\n \n <tr>\n \n <th>DataElement (\n <a href=\"http://hl7.org/fhir/StructureDefinition/dataelement-sdc-de\">Profile</a>)\n </th>\n \n <td>\n \n <a title=\"Allows a user to search for existing data elements\" href=\"#DataElement-search-type\">SHALL</a>\n \n </td>\n \n <td>\n \n <a title=\"Allows retrieval of a specific known data element\" href=\"#DataElement-read\">SHALL</a>\n \n </td>\n \n <td>\n \n <a title=\"Allows retrieval of a specific version of a data element\" href=\"#DataElement-vread\">SHALL</a>\n \n </td>\n \n <td>\n \n <a title=\"Allows review of changes to a data element over time\" href=\"#DataElement-history-instance\">SHALL</a>\n \n </td>\n \n <td/>\n \n <td>\n \n <a title=\"Allows defining a new data element. Repositories requiring curation of submitted data elements may require all new data elements to have a status of 'draft'.\" href=\"#DataElement-create\">SHALL</a>\n \n </td>\n \n <td>\n \n <a title=\"Allows maintaining data elements, such as adding additional mappings, display names, etc. Servers may choose to prohibit certain types of edits, instead requiring the creation of a new data element (and potentially the retiring of the existing data element). Servers may also limit who can change particular data elements.\" href=\"#DataElement-update\">SHALL</a>\n \n </td>\n \n <td>\n \n <a title=\"Allows removal of an existing data element. Servers may choose to not support deletions or may limit deletions to data elements meeting certain requirements. E.g. only elements with a status of draft or only elements that have been retired for at least two years, etc.\" href=\"#DataElement-delete\">MAY</a>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>ValueSet (\n <a href=\"http://hl7.org/fhir/StructureDefinition/valueset-sdc-de\">Profile</a>)\n </th>\n \n <td>\n \n <a title=\"Allows discovery of existing value sets for use in authoring data elements\" href=\"#ValueSet-search-type\">SHALL</a>\n \n </td>\n \n <td>\n \n <a title=\"Allows retrieval of a specific value set referenced within a data element\" href=\"#ValueSet-read\">SHALL</a>\n \n </td>\n \n <td>\n \n <a title=\"Allows retrieval of a historical version of a value set as referenced within a data element\" href=\"#ValueSet-vread\">SHALL</a>\n \n </td>\n \n <td>\n \n <a title=\"Allows review of changes to a value set over time\" href=\"#ValueSet-history-instance\">SHALL</a>\n \n </td>\n \n <td/>\n \n <td>\n \n <a title=\"Allows definition of a new value set used by one or more data elements\" href=\"#ValueSet-create\">SHALL</a>\n \n </td>\n \n <td>\n \n <a title=\"Allows existing value sets referenced by one or more data elements to be maintained\" href=\"#ValueSet-update\">SHALL</a>\n \n </td>\n \n <td>\n \n <a title=\"Not all servers will support deletion of value sets. Status change to 'retired' will be more typical, though deletion of draft value sets may keep repositories cleaner.\" href=\"#ValueSet-delete\">MAY</a>\n \n </td>\n \n </tr>\n \n </tbody>\n \n </table>\n \n <br/>\n \n <br/>\n \n <h3>\n \n <a href=\"../dataelement.html\">DataElement</a>\n \n </h3>\n \n <h4>Interactions</h4>\n \n <table class=\"list\">\n \n <thead>\n \n <tr>\n \n <th>Name</th>\n \n <th>Conformance</th>\n \n <th>Description</th>\n \n </tr>\n \n </thead>\n \n <tbody>\n \n <tr>\n \n <th>\n \n <a name=\"DataElement-search-type\"> </a>\n \n <span>search-type</span>\n \n </th>\n \n <td>SHALL</td>\n \n <td>\n \n <p>Allows a user to search for existing data elements</p>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>\n \n <a name=\"DataElement-read\"> </a>\n \n <span>read</span>\n \n </th>\n \n <td>SHALL</td>\n \n <td>\n \n <p>Allows retrieval of a specific known data element</p>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>\n \n <a name=\"DataElement-vread\"> </a>\n \n <span>vread</span>\n \n </th>\n \n <td>SHALL</td>\n \n <td>\n \n <p>Allows retrieval of a specific version of a data element</p>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>\n \n <a name=\"DataElement-history-instance\"> </a>\n \n <span>history-instance</span>\n \n </th>\n \n <td>SHALL</td>\n \n <td>\n \n <p>Allows review of changes to a data element over time</p>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>\n \n <a name=\"DataElement-create\"> </a>\n \n <span>create</span>\n \n </th>\n \n <td>SHALL</td>\n \n <td>\n \n <p>Allows defining a new data element. Repositories requiring curation of submitted data elements may require all new data elements to have a status of 'draft'.</p>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>\n \n <a name=\"DataElement-update\"> </a>\n \n <span>update</span>\n \n </th>\n \n <td>SHALL</td>\n \n <td>\n \n <p>Allows maintaining data elements, such as adding additional mappings, display names, etc. Servers may choose to prohibit certain types of edits, instead requiring the creation of a new data element (and potentially the retiring of the existing data element). Servers may also limit who can change particular data elements.</p>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>\n \n <a name=\"DataElement-validate\"> </a>\n \n <span>validate</span>\n \n </th>\n \n <td>SHOULD</td>\n \n <td>\n \n <p>Allows a client to verify whether a particular new data element or revision of an existing data element would be accepted based on validation and other business rules. Useful for some workflows</p>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>\n \n <a name=\"DataElement-delete\"> </a>\n \n <span>delete</span>\n \n </th>\n \n <td>MAY</td>\n \n <td>\n \n <p>Allows removal of an existing data element. Servers may choose to not support deletions or may limit deletions to data elements meeting certain requirements. E.g. only elements with a status of draft or only elements that have been retired for at least two years, etc.</p>\n \n </td>\n \n </tr>\n \n </tbody>\n \n </table>\n \n <br/>\n \n <br/>\n \n <h3>\n \n <a href=\"../valueset.html\">ValueSet</a>\n \n </h3>\n \n <h4>Interactions</h4>\n \n <table class=\"list\">\n \n <thead>\n \n <tr>\n \n <th>Name</th>\n \n <th>Conformance</th>\n \n <th>Description</th>\n \n </tr>\n \n </thead>\n \n <tbody>\n \n <tr>\n \n <th>\n \n <a name=\"ValueSet-search-type\"> </a>\n \n <span>search-type</span>\n \n </th>\n \n <td>SHALL</td>\n \n <td>\n \n <p>Allows discovery of existing value sets for use in authoring data elements</p>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>\n \n <a name=\"ValueSet-read\"> </a>\n \n <span>read</span>\n \n </th>\n \n <td>SHALL</td>\n \n <td>\n \n <p>Allows retrieval of a specific value set referenced within a data element</p>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>\n \n <a name=\"ValueSet-vread\"> </a>\n \n <span>vread</span>\n \n </th>\n \n <td>SHALL</td>\n \n <td>\n \n <p>Allows retrieval of a historical version of a value set as referenced within a data element</p>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>\n \n <a name=\"ValueSet-history-instance\"> </a>\n \n <span>history-instance</span>\n \n </th>\n \n <td>SHALL</td>\n \n <td>\n \n <p>Allows review of changes to a value set over time</p>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>\n \n <a name=\"ValueSet-create\"> </a>\n \n <span>create</span>\n \n </th>\n \n <td>SHALL</td>\n \n <td>\n \n <p>Allows definition of a new value set used by one or more data elements</p>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>\n \n <a name=\"ValueSet-update\"> </a>\n \n <span>update</span>\n \n </th>\n \n <td>SHALL</td>\n \n <td>\n \n <p>Allows existing value sets referenced by one or more data elements to be maintained</p>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>\n \n <a name=\"ValueSet-validate\"> </a>\n \n <span>validate</span>\n \n </th>\n \n <td>SHOULD</td>\n \n <td>\n \n <p>Allows verification that a value set is valid prior to submission - useful for some workflows.</p>\n \n </td>\n \n </tr>\n \n <tr>\n \n <th>\n \n <a name=\"ValueSet-delete\"> </a>\n \n <span>delete</span>\n \n </th>\n \n <td>MAY</td>\n \n <td>\n \n <p>Not all servers will support deletion of value sets. Status change to 'retired' will be more typical, though deletion of draft value sets may keep repositories cleaner.</p>\n \n </td>\n \n </tr>\n \n </tbody>\n \n </table>\n \n </div>"
},
"name": "SDC Data Element Curator",
"status": "draft",
"publisher": "U.S. Office of the National Coordinator (ONC)",
"contact": [
{
"telecom": [
{
"system": "other",
"value": "http://wiki.siframework.org/Structured+Data+Capture+Initiative"
}
]
}
],
"date": "2014-07-06",
"description": "This profile defines the expected capabilities of the ''SDC Data Element Curator'' role when conforming to the S&I Framework's [[sdc|Structured Data Capture FHIR Data Element Exchange implementation guide]]. This role is responsible for defining and updating data elements stored in a repository.",
"kind": "requirements",
"fhirVersion": "1.0.2",
"acceptUnknown": "extensions",
"format": [
"xml",
"json"
],
"rest": [
{
"mode": "server",
"documentation": "The primary focus of the curator is the definition and maintenance of [[DataElement]]s. However, [[ValueSet]]s must also be supported to allow definition of coded data elements. Some data elements will choose to maintain value sets as 'contained' resources, meaning the value set exists only in the context of the data element and cannot be referenced or maintained without also updating the data element. However, systems should support value set re-use across data elements. (Version-specific referencing can be used to avoid value sets from changing independent of the referencing [[Questionnaire]].)",
"security": {
"description": "Implementations must meet the general security requirements documented in the [[sdc-security|SDC implementation guide]]."
},
"resource": [
{
"type": "DataElement",
"profile": {
"reference": "http://hl7.org/fhir/StructureDefinition/dataelement-sdc-de"
},
"interaction": [
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "SHALL"
}
],
"code": "search-type",
"documentation": "Allows a user to search for existing data elements"
},
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "SHALL"
}
],
"code": "read",
"documentation": "Allows retrieval of a specific known data element"
},
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "SHALL"
}
],
"code": "vread",
"documentation": "Allows retrieval of a specific version of a data element"
},
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "SHALL"
}
],
"code": "history-instance",
"documentation": "Allows review of changes to a data element over time"
},
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "SHALL"
}
],
"code": "create",
"documentation": "Allows defining a new data element. Repositories requiring curation of submitted data elements may require all new data elements to have a status of 'draft'."
},
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "SHALL"
}
],
"code": "update",
"documentation": "Allows maintaining data elements, such as adding additional mappings, display names, etc. Servers may choose to prohibit certain types of edits, instead requiring the creation of a new data element (and potentially the retiring of the existing data element). Servers may also limit who can change particular data elements."
},
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "SHOULD"
}
],
"code": "validate",
"documentation": "Allows a client to verify whether a particular new data element or revision of an existing data element would be accepted based on validation and other business rules. Useful for some workflows"
},
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "MAY"
}
],
"code": "delete",
"documentation": "Allows removal of an existing data element. Servers may choose to not support deletions or may limit deletions to data elements meeting certain requirements. E.g. only elements with a status of draft or only elements that have been retired for at least two years, etc."
}
]
},
{
"type": "ValueSet",
"profile": {
"reference": "http://hl7.org/fhir/StructureDefinition/valueset-sdc-de"
},
"interaction": [
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "SHALL"
}
],
"code": "search-type",
"documentation": "Allows discovery of existing value sets for use in authoring data elements"
},
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "SHALL"
}
],
"code": "read",
"documentation": "Allows retrieval of a specific value set referenced within a data element"
},
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "SHALL"
}
],
"code": "vread",
"documentation": "Allows retrieval of a historical version of a value set as referenced within a data element"
},
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "SHALL"
}
],
"code": "history-instance",
"documentation": "Allows review of changes to a value set over time"
},
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "SHALL"
}
],
"code": "create",
"documentation": "Allows definition of a new value set used by one or more data elements"
},
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "SHALL"
}
],
"code": "update",
"documentation": "Allows existing value sets referenced by one or more data elements to be maintained"
},
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "SHOULD"
}
],
"code": "validate",
"documentation": "Allows verification that a value set is valid prior to submission - useful for some workflows."
},
{
"extension": [
{
"url": "http://hl7.org/fhir/StructureDefinition/conformance-expectation",
"valueCode": "MAY"
}
],
"code": "delete",
"documentation": "Not all servers will support deletion of value sets. Status change to 'retired' will be more typical, though deletion of draft value sets may keep repositories cleaner."
}
]
}
]
}
]
}
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.
© HL7.org 2011+. FHIR DSTU2 (v1.0.2-7202) generated on Sat, Oct 24, 2015 07:44+1100.
Links: Search |
Version History |
Table of Contents |
Compare to DSTU1 |
|
Propose a change